Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1809

reference: 114-tree-1
name: 1809
tree-preservation-order: undefined
114-tpo-1
uprn
address-text
point: POINT (-0.979054 50.859341)
geometry: MULTIPOLYGON (((-0.978955 50.859331,-0.978959 50.859350,-0.978973 50.859368,-0.978995 50.859382,-0.979022 50.859391,-0.979053 50.859394,-0.979084 50.859392,-0.979112 50.859383,-0.979134 50.859369,-0.979149 50.859352,-0.979154 50.859332,-0.979149 50.859313,-0.979136 50.859295,-0.979114 50.859281,-0.979086 50.859272,-0.979056 50.859269,-0.979025 50.859271,-0.978997 50.859280,-0.978975 50.859294,-0.978960 50.859311,-0.978955 50.859331)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL